<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5524/How-Enterprise-Architecture-can-reduce-risk-in-Mergers-and-Acquisitions.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5524</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5524&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How Enterprise Architecture can reduce risk in Mergers and Acquisitions</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5524/How-Enterprise-Architecture-can-reduce-risk-in-Mergers-and-Acquisitions.aspx</link> 
    <description>Corporate mergers and acquisitions (M&amp;amp;A) continue as a critical means for enterprises to meet strategic objectives such as growing market share or acquiring new capabilities. However, rate of successful outcomes has not grown at the same pace as the number or M&amp;amp;As themselves. In this post, Dr. Coghill argues the case for using enterprise architecture to provide increased visibility and clarity around M&amp;amp;A objectives to support improved outcomes.&amp;nbsp;</description> 
    <dc:creator>coghillc</dc:creator> 
    <pubDate>Sun, 19 Jan 2020 18:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5524</guid> 
    
</item>

    </channel>
</rss>